Control or primary recovery area disk
The procedure you follow to recover from a full disk depends on whether the variable-length BI extent is on the full disk. Because the BI extent grows during the crash recovery phase of the database startup, if the BI extent is on the full disk, you cannot start the database.
|
To recover from a full disk if the BI file is not on the full disk: |
- Truncate the BI file using the PROUTIL TRUNCATE BI utility. This rolls back any transactions active at the time the database shuts down. You can also start a single-user OpenEdge session to accomplish the same thing.
- Add one or more data extents to the database using the PROSTRCT ADD utility. This step is not necessary to bring the database back online. However, if you omit this step, the database will shut down when users begin adding data to it.
- Restart the database.
If you have no additional disk space, you must install a new disk or delete some data from the database before you can bring the database online.
|
|
To recover from a full disk if the BI file is on the full disk: |
- Use the PROSTRCT ADD utility to add a BI extent on a disk that contains some free space. The maximum amount of additional BI space you require to recover the database is equal to that currently consumed by the BI file. If you have a disk with this much free space, then assign the new BI extent to that volume. Note that this is a worst-case space requirement and the BI file normally grows much less than this. Adding the BI extent makes the variable length extent a fixed-length extent.
- Start a single-user OpenEdge session against the database. This begins database crash recovery. Exit the single-user session.
- Restart the database.